Released on: October 20, 2008, 3:17 pm

Press Release Author: Alba Spectrum LLC

Industry: Computers

Press Release Summary: SAP B1 initial data migration and conversion is typically
done through Data Transfer Workbench, where you basically use CSV Excel templates,
fill them in with required fields, leave everything optional blank, build
integration on the fly and run it with series of tests and rollbacks until you are
satisfied with the data massage and migration quality.

Press Release Body: SAP B1 initial data migration and conversion is typically done
through Data Transfer Workbench, where you basically use CSV Excel templates, fill
them in with required fields, leave everything optional blank, build integration on
the fly and run it with series of tests and rollbacks until you are satisfied with
the data massage and migration quality. It is also good idea to copy your
production company database into the test company and probe the data import there
first. Let's try to break through MS Excel restrictions and see how you could place
into production something more complex, ongoing integration, for example. In this
publication we will just mention, that real time integration could be programmed in
SAP Business One SDK, however this is outside of the scope

1. ODBC integration. At this time ODBC source integration could not be scheduled
for automatic run via batch command, as SAP doesn't support this and it doesn't
work. The way you do advanced ODBC integration - you create SQL view which has
exactly the same column names as you see in CSV template for the intended objects.
And you will have to provide enumerated column in your view for RecordKey

2. Scheduled Run. The work around to schedule ongoing integration is to create Data
Transformation Package, which will import text file (try this nice construction:
Microsoft.Jet.OLEDB.4.0, instead of creating linked server), then it will transform
the data via SQL stored procedure (feel free to create temporary staged tables, SQL
cursors, etc.). Then it will export your data from SQL to CSV file, ready for
integration. You can build and save DTW integration, and schedule it in the batch
file, assuming that it will work off the CSV templates

3. DTW limitations. Current SB1 version 2007A doesn't have all the SAP Business One
objects covered, or at least we found some objects, which we had to move into SAP BO
through SDK small add-ons. Open Inventory, Item Management, Alternative Items -
there are no template for Alternatives and you have to push them into SBO through
SDK to avoid problems with Early Watch Alert


Web Site: http://www.albaspectrum.com

Contact Details: Andrew Karasev, Alba Spectrum LLC, help@albaspectrum.com,
http://www.albaspectrum.com, 1-866-528-0577 , subdivision of M2-D2, SAP Business
One VAR and Reseller in Illinois, Georgia, South Carolina, California, Texas. Please
visit our info portal Pegas Planet: http://www.pegasplanet.com Local Service in
Chicago, Atlanta, San Diego, Los Angeles, Orange County, Houston. We also have SAP
Business One Software Development Factory and SB1 Technical Support Call Center,
serving USA country side businesses and internationally: Canada, Brazil. Illinois
practice: Naperville, Aurora, Plainfield, Marseilles, Ottawa, DeKalb, Springfield,
Oakbrook, Glenn Ellyn, Wheaton, Bolingbrook, Romeoville, Lisle, Melrose Park,
Brookfield. San Diego and LA practice: Rancho Bernardo, Oceanside, Poway, Long
Beach, Irvine, Mission Viejo, San Marcos, Carlsbad, La Jolla, Escondido. Houston
Practice: Dallas, Galveston, Sugar Land, Pearland, Katy, Pasadena, Rosenberg, League
City, Galena Park